-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(dev-server): configure request proxy for dev-server #1299
Conversation
Great idea, I didn't know the devserver had such an ability. This is definitely easier than dealing with CORS. |
Seems like some paths are constructed incorrectly and this setup exposes the flaws: Notice the double Similar problem occurs for archived recordings' reports: |
Nice thanks for catching that! I fixed the URL construct for that now. It should work as expected. |
In the 2 latest commits, I added some changes that ensure dev-server work with cryostat over https: cryostatio/cryostat#426. |
Welcome to Cryostat! 👋
Before contributing, make sure you have:
main
branch[chore, ci, docs, feat, fix, test]
To recreate commits with GPG signature
git fetch upstream && git rebase --force --gpg-sign upstream/main
Fixes: cryostatio/cryostat#328
Related to cryostatio/cryostat#327
Description of the change:
Motivation for the change:
This should allow development of web without having to rebuild the container image all the time. I think this is a bit simpler than handling CORS.
This idea comes from the fact that Grafana proxies its client's requests to jfr-datasource so I guess dev-server can do the same. What do you think @andrewazores?
References
https://webpack.js.org/configuration/dev-server/#devserverproxy